What

ChatMessage and VectorStoreQuery already skip their Enter handler while an IME is composing:

const isIMEComposition = e.isComposing || e.keyCode === 229
if (e.key === 'Enter' && ... && !isIMEComposition) { ... }

A few other single-line text inputs handle Enter on keydown but don't have that check, so they act while the user is still composing.

Why

When typing with an IME (Japanese, Chinese, Korean, and macOS dead keys), the Enter that confirms a candidate fires a keydown with key === 'Enter' (and keyCode === 229 / isComposing === true) before compositionend. Without a guard, that first confirmation Enter is treated as a submit, so:

• Canvas header: the flow name is saved and edit mode closes on the first IME confirmation, before the user has finished the name.
• Save chatflow dialog: the dialog confirms on the confirmation key.
• Tag dialog and Export-as-template dialog: a half-composed string gets added as a tag / usecase.

The result is that a CJK user cannot reliably type a multi-character word in these fields.

Change

Apply the same guard the repo already uses in ChatMessage and VectorStoreQuery to the inputs that were missing it:

• views/canvas/CanvasHeader.jsx (flow name rename)
• ui-component/dialog/SaveChatflowDialog.jsx (save name)
• ui-component/dialog/TagDialog.jsx (add tag)
• ui-component/dialog/ExportAsTemplateDialog.jsx (add usecase)

For a normal keystroke isComposing is false and keyCode is 13, so the guard is a no-op and existing behavior is unchanged. Escape handling is left as-is.

Testing

I didn't have an IME set up to reproduce this directly. I confirmed the changed files build and that the guard expression is identical to the one already shipping in ChatMessage / VectorStoreQuery. A manual check with a Japanese or Chinese IME in these four fields would be welcome to confirm.